HTTP request methods must be limited.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-92759	AS24-U1-001000	SV-102847r1_rule		Medium

Description
The HTTP 1.1 protocol supports several request methods that are rarely used and potentially high risk. For example, methods such as PUT and DELETE are rarely used and should be disabled in keeping with the primary security principal of minimize features and options. Also, since the usage of these methods is typically to modify resources on the web server, they should be explicitly disallowed. Normal web server operation will typically require allowing only the GET, HEAD, and POST request methods. This will allow for downloading of web pages and submitting information to web forms. The OPTIONS request method will also be allowed as it is used to request which HTTP request methods are allowed.

Description

The HTTP 1.1 protocol supports several request methods that are rarely used and potentially high risk. For example, methods such as PUT and DELETE are rarely used and should be disabled in keeping with the primary security principal of minimize features and options. Also, since the usage of these methods is typically to modify resources on the web server, they should be explicitly disallowed. Normal web server operation will typically require allowing only the GET, HEAD, and POST request methods. This will allow for downloading of web pages and submitting information to web forms. The OPTIONS request method will also be allowed as it is used to request which HTTP request methods are allowed.

STIG	Date
Apache Server 2.4 UNIX Server Security Technical Implementation Guide	2019-05-23

Details

Check Text ( C-92065r2_chk )
Determine the location of the "HTTPD_ROOT" directory and the "httpd.conf" file: # httpd -V \| egrep -i 'httpd_root\|server_config_file' -D HTTPD_ROOT="/etc/httpd" -D SERVER_CONFIG_FILE="conf/httpd.conf" Enter the following command into a command line: more <'INSTALLED PATH'>/conf/httpd.conf For every enabled "Directory" directive (except root), verify the following entry exists: Require all denied If the statement above is found in the "LimitExcept" statement (i.e., ), this is a finding. If the statement above is found enabled but without the appropriate "LimitExcept" or "Order" statement, this is a finding. If the statement is not found inside an enabled "Directory" directive, this is a finding. NOTE: If the "LimitExcept" statement above is operationally limiting, this should be explicitly documented and approved by the ISSO, at which point this can be considered not a finding.

Check Text ( C-92065r2_chk )

Determine the location of the "HTTPD_ROOT" directory and the "httpd.conf" file:

# httpd -V | egrep -i 'httpd_root|server_config_file'
-D HTTPD_ROOT="/etc/httpd"
-D SERVER_CONFIG_FILE="conf/httpd.conf"

Enter the following command into a command line:

more <'INSTALLED PATH'>/conf/httpd.conf

For every enabled "Directory" directive (except root), verify the following entry exists:

Require all denied

If the statement above is found in the "LimitExcept" statement (i.e., ), this is a finding.

If the statement above is found enabled but without the appropriate "LimitExcept" or "Order" statement, this is a finding.

If the statement is not found inside an enabled "Directory" directive, this is a finding.

NOTE: If the "LimitExcept" statement above is operationally limiting, this should be explicitly documented and approved by the ISSO, at which point this can be considered not a finding.

Fix Text (F-99003r1_fix)
Edit the "httpd.conf" file and add the following entries for every enabled "Directory" directive (except root). Require all denied Example: . . . # Limit HTTP methods Require all denied